On 30/12/23 30/12/23, 12:04, Shiv Shankar Dayal wrote:
It would be nice to either support Metapost 3D
Very simple MP pseudo 3D is included in
tex/texmf-context/metapost/context/base/mpiv/mp-tres.mpiv
Alan
designsize rm 12pt' is loaded
> metapost> initializing instance 'metafun:1' using format 'metafun'
> and method 'default'
> metapost> loading 'metafun' as
> '/usr/share/texmf/metapost/context/base/mpiv/metafun.mpiv' using method
> 'default'
> metapost>
'default'
metapost> loading 'metafun' as
'/usr/share/texmf/metapost/context/base/mpiv/metafun.mpiv' using method
'default'
metapost> initializing number mode 'scaled'
input stack overflow
mtx-context | fatal error: return code: 256
Commenting out "StartPage"
d method 'default'
metapost> loading 'metafun' as
'/usr/share/texmf/metapost/context/base/mpiv/metafun.mpiv' using method
'default'
metapost> initializing number mode 'scaled'
input stack overflow
mtx-context | fatal error: return code: 256
MWE from the documentation:
\us
>>> I made an experiment to add alternatives to sidebars (see attachment).
>>>
>>> I discovered the sidebar is drawn by anch_sidebars_draw in
>>> metapost/context/base/mpiv/mp-apos.mpiv.
>>>
>>> I've redefined it locally to add alternative
Il 28/04/21 17:53, Hans Hagen ha scritto:
On 4/28/2021 5:27 PM, mf wrote:
Hello,
I made an experiment to add alternatives to sidebars (see attachment).
I discovered the sidebar is drawn by anch_sidebars_draw in
metapost/context/base/mpiv/mp-apos.mpiv.
I've redefined it locally to add
On 4/28/2021 5:27 PM, mf wrote:
Hello,
I made an experiment to add alternatives to sidebars (see attachment).
I discovered the sidebar is drawn by anch_sidebars_draw in
metapost/context/base/mpiv/mp-apos.mpiv.
I've redefined it locally to add alternatives.
To make fancy, zig zag bars I
Hello,
I made an experiment to add alternatives to sidebars (see attachment).
I discovered the sidebar is drawn by anch_sidebars_draw in
metapost/context/base/mpiv/mp-apos.mpiv.
I've redefined it locally to add alternatives.
To make fancy, zig zag bars I defined a macro, draw_pattern_bar
pair)
> > I don't know, but from the message it looks like some 'local'
> variables
> > is not saved and defined. I'm surprised that loading some mf file
> works
> > at all (because it also assumes some mf related definitions). I also
> > hav
> > eno clue
t; metafun > log > error: Equation cannot be performed (numeric=pair)
I don't know, but from the message it looks like some 'local' variables
is not saved and defined. I'm surprised that loading some mf file works
at all (because it also assumes some mf related definitions). I a
I don't know, but from the message it looks like some 'local' variables
> is not saved and defined. I'm surprised that loading some mf file works
> at all (because it also assumes some mf related definitions). I also hav
> eno clue if such a package adopts 'core' metafun code (and mpiv meta
a package adopts 'core' metafun code (and mpiv metafun
is different from mpii).
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
te
to what extend updates to those engines have side effects for context,
but I assume none. Let me know if there are problems.
The MKIV code (mkiv, mkvi, mpiv, lua files) has changed but not much,
mostly as a side effect of the code split and move to LMTX where the
focus is on now. There have
On 1/27/2021 3:08 PM, Rudd, Kevin wrote:
thanks, Hans---
with the only change being the lmtx release, I get:
in 2020.09.20:
resolvers > tex > 'file' closer:
'/local/Software/lmtx/tex/texmf-context/metapost/context/base/mpiv/metafun.mpxl'
closed
metapost
ame
'/Users/janneman/context-osx-64/tex/texmf-context/tex/context/base/mkiv/meta-imp-dum.mkiv'
metapost> library 'dum' is loaded
metapost> initializing instance 'metafun:1' using format 'metafun' and
method 'default'
metapost> loading 'metafun' as
'/Users/janne
dum' is loaded
metapost> initializing instance 'metafun:1' using format 'metafun' and
method 'default'
metapost> loading 'metafun' as
'/Users/janneman/context-osx-64/tex/texmf-context/metapost/context/base/mpiv/metafun.mpxl'
using method 'default'
metapost>
ding latin modern fonts (second stage)
> > fonts > 'fallback modern-designsize rm 12pt' is loaded
> > metapost> initializing instance 'doublefun:1' using format
> > 'metafun' and method 'double'
> > metapost> loading 'metafun' as
> >
en making vardef's one need to omit the final
semi colon in order to apply more properties to the 'return value'.
At some point I will update the metafun manual which means: remove old
methods and exclusively use the new ones (currently the manual also
discusses mpii while in context mkiv/lm
lts in:
>>>
>>> system > files > jobname 'testcolor', input './testcolor', result
>>> 'testcolor'
>>> fonts > latin modern fonts are not preloaded
>>> languages > language 'en' is active
>>> open source
>> 'testcolor'
>> fonts > latin modern fonts are not preloaded
>> languages > language 'en' is active
>> open source > level 2, order 3, name './testcolor.tex'
>> fonts > preloading latin modern fonts (second stage)
>> fonts
modern fonts (second stage)
> fonts > 'fallback modern-designsize rm 12pt' is loaded
> metapost > initializing instance 'doublefun:1' using format 'metafun'
> and method 'double'
> metapost> loading 'metafun' as
> '/usr/local/context-osx-64/tex/texmf-c
el 2, order 3, name './testcolor.tex'
fonts > preloading latin modern fonts (second stage)
fonts > 'fallback modern-designsize rm 12pt' is loaded
metapost> initializing instance 'doublefun:1' using format 'metafun'
and method 'double'
metapost > loading '
This is a dirty hack to change the color of the crop marks and the page
number at the corner of a page when \setuplayout[marking=on].
Edit the file:
tex/texmf-context/metapost/context/base/mpiv/mp-crop.mpiv
in the distribution, changing two lines:
- (here i'm reproducing only the last
ound for the page.
> I've seen there's something about that in the mailing list history. I'll look
> into that.
>
> BTW, the MP file producing the marks is
>
> metapost/context/base/mpiv/mp-crop.mpiv
Sorry for mixing up marks and markings.
> Am 2019-12-19 um 19:08 schrieb Han
for the page.
I've seen there's something about that in the mailing list history. I'll
look into that.
BTW, the MP file producing the marks is
metapost/context/base/mpiv/mp-crop.mpiv
Massi
___
If your question
nstance 'metafun:1' using format 'metafun' and
method 'default'
metapost> loading 'metafun' as
'd:/Ctx-Beta/tex/texmf-context/metapost/context/base/mpiv/metafun.mpiv' using
method 'default'
metapost> initializing number mode 'scaled'
tex error > mp erro
t-test.tex'
fonts > preloading latin modern fonts (second stage)
fonts > 'fallback modern-designsize rm 12pt' is loaded
metapost > initializing instance 'metafun:1' using format
'metafun' and method 'default'
metapost > loading 'metafun' as
nts > 'fallback modern-designsize rm 12pt' is loaded
metapost> initializing instance 'metafun:1' using format 'metafun' and
method 'default'
metapost> loading 'metafun' as
'C:/Users/Hermann/Downloads/context-mswin/tex/texmf-context/metapost/context/base/mpiv/meta
gt; I was using metapost to generate some symbols, as in
> "tex/texmf-context/metapost/context/fonts/mpiv/demo-symbols.tex"
How do you use these symbols in a document? Do you call them up by
number somehow? Using some glyph interface doesn't make much sense I
think, as the font s
On 7/5/2019 8:32 AM, Zhichu wrote:
Hi everyone,
I was using metapost to generate some symbols, as in
"tex/texmf-context/metapost/context/fonts/mpiv/demo-symbols.tex"
How do you use these symbols in a document? Do you call them up by
number somehow? Using some glyph interface do
Hi everyone,
I was using metapost to generate some symbols, as in
"tex/texmf-context/metapost/context/fonts/mpiv/demo-symbols.tex"
Occasionally, I want to customize a glyph whose charcode is a little large, say
the character "院":
=
ck modern-designsize rm 12pt' is loaded
metapost > initializing instance 'metafun' using format 'metafun'
metapost> loading 'metafun' as
'/usr/share/texmf/metapost/context/base/mpiv/metafun.mpiv' using method
'default' metapost> initializing number mode 'scaled'
'gnuplot-gnuplot-1-ctx.tex'
close source > level 3, order 6, name 'gnuplot-gnuplot-1-ctx.tex'
metapost > initializing instance 'metafun:1' using format
'metafun' and method 'default'
metapost > loading 'metafun' as
'/home/user/context/tex/texmf-context/metapost/context/b
un'
and method 'default'
metapost> loading 'metafun' as
'/home/user/context/tex/texmf-context/metapost/context/base/mpiv/metafun.mpiv'
using method 'default'
metapost> initializing number mode 'scaled'
floatblocks > '1' placed (here)
from a lmtx-run (no .plt-file and -c
at and to be honest am not too motivated to support mpiv code in
generic either .. better use
Until TeX Live 2018, MetaFun worked in plain (at least the subset I'm
using). It would be a shame if the support would end. I also think
that there are quite a number of users. The number of posts
ATEXFUNCTIONALITY)") ;
instead of
numeric LUATEXFUNCTIONALITY ; LUATEXFUNCTIONALITY :=
runscript("mp.print(LUATEXFUNCTIONALITY)") ;
Now I have
tex/texmf-context/metapost/context/base/mpiv$ grep -r LUATEXFUNCTIONALITY
mp-mlib.mpiv:%numeric LUATEXFUNCTIONALITY ; LUATEXFUNCTIONALITY :=
runscrip
XFUNCTIONALITY or 0)
>
> but ... i'm surprised you can use metafun in plain at all ... i never
> test that and to be honest am not too motivated to support mpiv code in
> generic either .. better use
Until TeX Live 2018, MetaFun worked in plain (at least the subset I'm
using). It
ecute[[
> boolean mplib ; mplib := true ;
> input metafun.mp ;
> ]]
>
> print(ret.log)
> }
> \bye
>
>
in mp-mlib.mpiv it seems that we should have
string LUATEXFUNCTIONALITY ; LUATEXFUNCTIONALITY :=
runscript("mp.print(LUATEXFUNCTIONALITY)") ;
instead of
numeri
ATEXFUNCTIONALITY)"
! Equation cannot be performed (numeric=string).
hm, that can be
mp.print(LUATEXFUNCTIONALITY or 0)
but ... i'm surprised you can use metafun in plain at all ... i never
test that and to be honest am not too motivated to support mpiv code in
generic either .. bet
rce > level 2, order 3, name
'/Users/fabricel/Dropbox/Divers/Création/P030-Remplissage/0030-0018-minimal2.tex'
fonts > preloading latin modern fonts (second stage)
fonts > 'fallback modern-designsize rm 12pt' is loaded
metapost > initializing instance 'metafun' using
aded
metapost> initializing instance 'metafun' using format 'metafun'
metapost> loading 'metafun' as
'/Users/fabricel/context/tex/texmf-context/metapost/context/base/mpiv/metafun.mpiv'
using method 'default'
metapost> initializing number mode 'scaled'
tex error
ntext/base/mkiv/cont-new.mkiv'
> > system > files > jobname 'vladimir', input './vladimir', result
> > 'vladimir'
> > fonts > latin modern fonts are not preloaded
> > languages > language 'en' is active
> > open source > level 2
age 'en' is active
> open source > level 2, order 3, name '/home/aragorn/vladimir.tex'
> system > synctex functionality is enabled, expect 5-10 pct runtime
> overhead!
> fonts > preloading latin modern fonts (second stage)
> fonts > 'fallback
tage)
fonts > 'fallback modern-designsize rm 12pt' is loaded
structure > sectioning > chapter @ level 2 : 0.1 -> First chapter
metapost> initializing instance 'metafun:1' using format 'metafun'
and method 'default'
metapost> loading 'metafun' as
'/h
input './vladimir', result
>> > 'vladimir'
>> > fonts > latin modern fonts are not preloaded
>> > languages > language 'en' is active
>> > open source > level 2, order 3, name '/home/aragorn/vladimir.tex'
>> > system >
'/home/aragorn/vladimir.tex'
> > system > synctex functionality is enabled, expect 5-10 pct
> runtime
> > overhead!
> > fonts > preloading latin modern fonts (second stage)
> > fonts > 'fallback modern-designsize rm 12pt' is loaded
> &g
runtime
> overhead!
> fonts > preloading latin modern fonts (second stage)
> fonts > 'fallback modern-designsize rm 12pt' is loaded
> structure > sectioning > chapter @ level 2 : 0.1 -> First chapter
> metapost> initializing instance 'metaf
modern-designsize rm 12pt' is loaded
structure > sectioning > chapter @ level 2 : 0.1 -> First chapter
metapost> initializing instance 'metafun:1' using format 'metafun'
and method 'default'
metapost> loading 'metafun' as
'/home/aragorn/context/tex/texmf-co
ignsize rm 12pt' is loaded
structure > sectioning > chapter @ level 2 : 0.1 -> First chapter
metapost> initializing instance 'metafun:1' using format
'metafun' and method 'default'
metapost> loading 'metafun' as
'/home/aragorn/context/tex/texmf-context/metapost/c
> preloading latin modern fonts (second stage)
fonts > 'fallback modern-designsize rm 12pt' is loaded
structure > sectioning > chapter @ level 2 : 0.1 -> First chapter
metapost> initializing instance 'metafun:1' using format 'metafun'
and method 'defau
pouf.tex'
fonts > preloading latin modern fonts (second stage)
fonts > 'fallback modern-designsize rm 12pt' is loaded
structure > sectioning > chapter @ level 2 : 0.1 -> First chapter
metapost> initializing instance 'metafun:1' using format 'metafun'
and meth
; xmp > using file
'/home/aragorn/context/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml'
pages > flushing realpage 1, userpage 1, subpage 1
structure > sectioning > chapter @ level 2 : 0.1 -> Espaces
probabilisés
metapost> initializing instance
> preloading latin modern fonts (second stage)
> > fonts > 'fallback modern-designsize rm 12pt' is loaded
> > structure > sectioning > title @ level 2 : 0.0 -> Sommaire
> > backend > xmp > using file
> > '/home/aragorn/co
/context/base/mkiv/lpdf-pdx.xml'
> pages > flushing realpage 1, userpage 1, subpage 1
> structure > sectioning > chapter @ level 2 : 0.1 -> Espaces
> probabilisés
> metapost > initializing instance 'metafun:1' using format
> 'metafun' a
modern fonts (second stage)
fonts > 'fallback modern-designsize rm 12pt' is loaded
metapost> initializing instance 'metafun' using format 'metafun'
metapost> loading 'metafun' as
'/home/fab/context/tex/texmf-context/metapost/context/base/mpiv/metafun.mpiv'
using me
r 20, name '../setup_code.tex'
close source > level 4, order 20, name '../setup_code.tex'
close source > level 3, order 20, name '../setup_global.tex'
open source > level 3, order 21, name '../setup_frontmatter.tex'
structures > begin of sectionblock 'frontpart'
open source > leve
pen source > level 3, order 21, name '../setup_frontmatter.tex'
structures > begin of sectionblock 'frontpart'
open source > level 4, order 22, name 'title.tex'
metapost> initializing instance 'metafun' using format 'metafun'
metapost> loading 'metafu
rce > level 2, order 3, name 'D:/My Documents/graphic.tex'
fonts > preloading latin modern fonts (second stage)
fonts > 'fallback modern-designsize rm 12pt' is loaded
metapost> initializing instance 'metafun' using format 'metafun'
metapost>
nts (second stage)
fonts > 'fallback modern-designsize rm 12pt' is loaded
metapost> initializing instance 'metafun' using format 'metafun'
metapost> loading 'metafun' as
'/home/fab/context/tex/texmf-context/metapost/context/base/mpiv/metafun.mpiv'
using method 'd
On Mon, Jun 15, 2015 at 9:43 AM, Hans Hagen wrote:
On 6/14/2015 11:26 PM, Mojca Miklavec wrote:
On Fri, Jun 12, 2015 at 12:45 AM, Hans Hagen wrote:
Most shades look ugly and useless to me anyway but you have more control
than you think (always had but nicer interfaced in mpiv
On 6/14/2015 11:26 PM, Mojca Miklavec wrote:
On Fri, Jun 12, 2015 at 12:45 AM, Hans Hagen wrote:
Most shades look ugly and useless to me anyway but you have more control
than you think (always had but nicer interfaced in mpiv):
\startMPpage
fill fullcircle scaled 10cm
On Fri, Jun 12, 2015 at 12:45 AM, Hans Hagen wrote:
Most shades look ugly and useless to me anyway but you have more control
than you think (always had but nicer interfaced in mpiv):
\startMPpage
fill fullcircle scaled 10cm
withshademethod circular
withshadevector (5cm
think (always had but nicer interfaced in mpiv):
\startMPpage
fill fullcircle scaled 10cm
withshademethod circular
withshadevector (5cm,1cm)
withshadecenter (.1,.5)
withshadedomain (.2,.6)
withshadefactor 1.2
withshadecolors (red,green
On 2013–10–01 Hans Hagen wrote:
in mkiv the overhead is less than in mpii as we don't parse the blob
in the same way and the mpiv code is also more optimized so we can
consider dropping the SetPageState macro.
I see you decided to drop LoadPageState. It's about 20ms overhead
per 1000 graphics
On 10/1/2013 8:35 PM, Marco Patzer wrote:
On 2013–10–01 Hans Hagen wrote:
in mkiv the overhead is less than in mpii as we don't parse the blob
in the same way and the mpiv code is also more optimized so we can
consider dropping the SetPageState macro.
I see you decided to drop LoadPageState
“foo”:
The MpIV code has namespace protection. Why run traditional in MkIV?
\starttext
\startMPcode
label(first, origin);
%% MkIV
%% pair mfun_laboff.foo ; mfun_laboff.foo := (.5,-1) ;
%% mfun_labxf.foo := mfun_labyf.foo := 1 ;
%% MkII
pair laboff.foo
On 2013–08–23 Hans Hagen wrote:
Is this prefix required? It breaks old code and required a branch in
every new project. And I don't really see a reason for this
incompatibility. Here is an example defining a new direction “foo”:
The MpIV code has namespace protection. Why run traditional
On 8/23/2013 3:14 PM, Marco Patzer wrote:
On 2013–08–23 Hans Hagen wrote:
Is this prefix required? It breaks old code and required a branch in
every new project. And I don't really see a reason for this
incompatibility. Here is an example defining a new direction “foo”:
The MpIV code has
On 16-5-2012 01:45, Mojca Miklavec wrote:
Hello,
last year Taco added many patches to make sure that ConTeXt works even
when installed to C:\Documents and Settings\ ... and other weird
paths with spaces. However metapost in mkiv still fails. I figured out
that the following patch (which *won't*
On 16-5-2012 01:45, Mojca Miklavec wrote:
Maybe it would be helpful to pass
file.addsuffix(name,mp)
through additional filter (instead of simply adding quotation marks)
that would also check if any other character needs escaping and add
quotation marks if needed.
let's for the moment
Hello,
last year Taco added many patches to make sure that ConTeXt works even
when installed to C:\Documents and Settings\ ... and other weird
paths with spaces. However metapost in mkiv still fails. I figured out
that the following patch (which *won't* handle paths with quotation
marks properly)
level) for the backgrounds but more
placed might need patching. So, from now on we will also have different
files for mp: mpii and mpiv.
I uploaded a beta, so best do some testing right away as i might have
messed up,
Hans
72 matches
Mail list logo
